Fix the bug that accept attribute in the input field didn't work properly #2360
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What I did
accept
attribute in the input field didn't work.
, theIsAcceptedFile
validator always fails. (It tries to comparejpg
(from the accept attirbute) and.jpg
(from file name)hasFeedbackFor
property of thelion-input-file
from the inspector.
, the file dialog disable those file with the extensions (accept="jpg"
will make jpg files unselectable - actually all files become unselectible)Technically breaking change
Apparently we officially supported extensions without
.
for theaccept
attribute, but this is not a valid accept attribute and breaks the behaviour of browsers (tested on Chrome 128.0.6613.114, Mac). So I removed the normalization (removing.
) of the extension and the relevant test.It's technically a breaking change, but it seems rather a bug fix, to me (if a consumer used extensions without
.
, it would break the browser behavior, anyway)